PrizmDoc Application Services Database Administration & Maintenance

PrizmDoc Application Services (PAS) requires a database for the Pre-Conversion Services. Pre-Conversion Services are included as a "Developer Preview." This feature is in late-stage development and APIs marked as such should be used for evaluation purposes only and should not be used in production deployments. Note that these APIs may undergo change prior to feature completion. The Pre-Conversion Services will be feature complete in PrizmDoc version 11.1. This feature is off by default, and a database is not required to run PAS with Pre-Conversion disabled.

In the Developer Preview, an existing database must be provided to PAS in order to use the Pre-Conversion Services feature. You can see a list of supported databases in the PAS Configuration topic. After configuring the PAS with the correct information, some databases, like Microsoft SQL Server, will require that a script is run in order to set up the correct tables for that database. You can find out more information about this in the topic for setting up your database. Do note that PAS itself will only require read/write access to the database; running the mentioned scripts will require access to create and migrate tables.

Maintaining the Database

While directly reading, linking, or otherwise using the data stored in the database by PAS is discouraged, you will still need to do regular administrative tasks, such as taking proper snapshots and backups of the data in order to prevent and mitigate data loss.

In the event of data loss that requires recovery from a backup (both for the database or the local file storage) PAS has an API to validate viewing packages and their state. You can find out more about this API in the Viewing Package Validators developer reference.

Product and Database Updates

Once the Pre-Conversion feature is released, future updates to the product will contain the necessary logic or scripts to transition existing tables and data to the new format, provided that a schema change is necessary. You will be able to find out more about this in the product Release Notes in the event that a database migration is required in the future.